ci: stop queueing unavailable self-hosted gate - #132
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stops automatically queueing the optional self-hosted compatibility workflow on pull requests.
The repository currently has zero registered self-hosted runners, so every compatibility-relevant PR receives a
Compatibility Gatejob that can never start. The requiredCompatibility Gate (hosted runner)already runs the same QEMU/KVM validation on GitHub-hosted infrastructure and remains enforced by branch protection.The self-hosted workflow remains available through
workflow_dispatchfor operators that later register a suitable Linux x64 KVM runner.No tracking issue is required.
Security and release impact
Validation
go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.11go test ./...git diff --check